feat: add postgresql support#371
Open
fabioluciano wants to merge 9 commits into
Open
Conversation
- Introduced `httpRoute` configuration in `values.schema.json` and `values.yaml` to enable Gateway API HTTPRoute with customizable properties such as `gatewayName`, `hostnames`, and `prefix`. - Updated `values.yaml` to enable Grafana by default and set MySQL as the database type. - Added HTTPRoute resource for routing traffic to Grafana and UI services. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
fabioluciano
force-pushed
the
feature/postgresql-support
branch
from
192111a to
f832cb4
Compare
- Remove deprecated grafana.enabled=false requirement for PostgreSQL - Update note about Grafana compatibility with both MySQL and PostgreSQL - Add Gateway API HTTPRoute deployment scenario documentation - Regenerate charts/devlake/README.md with helm-docs to reflect: - httpRoute configuration options (9 new parameters) - grafana.enabled default changed to true - database.type default to mysql - database.externalPort updated to match database type
Grafana dashboards only support MySQL datasources. When using PostgreSQL, users must disable Grafana or use external Grafana instance.
…vice accounts in Helm templates
- Increase MySQL startup probe failureThreshold to 60 (310s total)
- Add comprehensive database smoke tests:
- MySQL: 6 tests (connectivity, version, charset, DB ops, user access)
- PostgreSQL: 7 tests (connectivity, version, encoding, table ops, permissions, config)
- Fix workflow to wait for DB pods specifically, not full stack
- Add helm install timeout (10m)
- Fix secret names in smoke tests (use ${RELEASE_NAME}-db-auth)
Fixes MySQL startup probe timeout in CI environments.
Author
|
This need to be approved first |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add PostgreSQL Support and Production Hardening
Summary
Major enhancement adding PostgreSQL database support alongside existing MySQL, plus comprehensive production hardening features including security controls, monitoring, backup capabilities, and extensive test coverage.
Key Features
Database Support
Production Readiness
Security Enhancements
automountServiceAccountToken: falseby defaultObservability
Testing & CI/CD
Documentation
Breaking Changes
None - fully backward compatible with existing MySQL deployments
Migration Path
Existing MySQL users: no action required
New users: choose
mysql.enabled: trueorpostgresql.enabled: trueTesting
Major additions:
templates/statefulset-postgresql.yaml- PostgreSQL StatefulSettemplates/statefulset-mysql.yaml- Separated MySQL StatefulSettemplates/networkpolicy-*.yaml- Network isolation policiestemplates/hpa.yaml- Horizontal pod autoscalingtemplates/backup-*.yaml- Backup CronJob and PVCtemplates/pre-install-validation.yaml- Pre-flight checks.github/scripts/*-smoke-test.sh- Database-specific test suitesvalues.schema.json- Configuration schema validation